Hello Tom,


I was hoping you might have a definitive list of messages that will get pumped through the new ErrorMsgCallback.

In .net the preferred method of handling errors is by throwing exceptions.

If I know what kind of messages to expect, I can add different types of exceptions that the end user programs can handle appropriately.



The situation I am trying to avoid is that everyone will have this ErrorReceived event handler that has the message(string) then people will have some sort of switch statement or if tree to parse out the particular error.

It will be much cleaner to handle this type of error discovery within the API via the aforementioned exceptions rather than everyone needing to implement their own.


Of course they will still be able to subscribe to the error text as well....

Thanks,

-Brad Murry